If you are installing any product on your Macintosh, it's always a good idea to reboot your machine first, then run the installer. In addition, running Disk First Aid or other disk repair utility is always a good idea before installing, since anything wrong with your disk may become a serious problem after installation.
If you have installed the debug version of OpenTransport on a NuBus Power Macintosh, you will ALWAYS get 2 UserBreaks when booting your machine. The first UserBreak will have no text associated with it, while the second will have the text "TLibrary::PrivateLoadSegment- Loading a Segment failed". Please do not report these as bugs.
PowerPC users - NOTE:
If you are installing Open Transport on a PowerPC machine, be sure to reboot your machine prior to installation, and do the installation immediately after the reboot is done. Even better, hold down the shift key during booting to disable all extension, then do the installation. If you do not do this, it is possible that the installer will crash during installation.
Also, if you have installed the debug version of OpenTransport on a NuBus Power Macintosh, you will ALWAYS get 2 UserBreaks when booting your machine. The first UserBreak will have no text associated with it, while the second will have the text "TLibrary::PrivateLoadSegment- Loading a Segment failed". Please do not report these as bugs. You can stop these messages from occurring by removing the file "Shared Library Manager PPC Dbg" from your extension folder and replacing it with the "Shared LibraryManager PPC" file from the non-debug installation. This will get rid of these UserBreaks, while still keeping the debug version of Open Transport installed.
MacTCP users - NOTE:
If you use an init that uses MacTCP ("Network Time" is one example) you must use the TCP/IP control panel in Advanced User mode to set TCP/IP to Load Always, and uncheck the box that says "Load on Demand". Due to the nature of the MacOS, with load on demand set, it is possible that TCP/IP will not be able to load due to lack of memory if there are Extensions that use MacTCP.
In addition, you must insure that any extensions that use MacTCP are renamed in such a way as to be loaded later than the "TCP/IP" control panel. You can insure this by renaming the Extension to start with a letter higher than "t" in the alphabet. A common way to insure this is to just precede the name of the Extension with the letter "z" (e.g. Rename "Network Time" to "zNetwork Time").
The installer will delete a prior installation of MacTCP and it's associated files. You may want to copy them to a safe place prior to installing Open Transport. However, also leave them installed so that Open Transport can convert the MacTCP configuration information automatically for you.
If you are installing over a version of Open Transport earlier than 1.0b3, you must manually remove the TCP/IP Preferences file from the "Preferences" folder in your System Folder. The current installer no longer deletes the "TCP/IP Preferences" file if it already exists, and version of the preference file earlier than 1.0b3 are NOT COMPATIBLE with the current version of the preference file. Failure to do this may cause your machine to crash when attempting to use TCP/IP.
Known Bugs/Incompatibilities
All users :
TCP/IP users :
• If you use an init that uses TCP/IP's MacTCP compatibility ("Network Time" is one example) you must use the TCP/IP control panel in Advanced User mode to set TCP/IP to Load Always, and uncheck the box that says "Load on Demand". Due to the nature of the MacOS, with load on demand set, it is possible that TCP/IP will not be able to load due to lack of memory if there are Extensions that use MacTCP.
In addition, you must insure that any extensions that use MacTCP are renamed in such a way as to be loaded later than the "TCP/IP" control panel. You can insure this by renaming the Extension to start with a letter higher than "t" in the alphabet. A common way to insure this is to just precede the name of the Extension with the letter "z" (e.g. Rename "Network Time" to "zNetwork Time").
•Users may want SLIP and/or PPP connections to happen automatically when an endpoint is opened (that is, from the user's point of view, when the networking application is executed). Open Transport does not support this with the currently available MDEVs. SLIP/PP connections must be started up using the 3rd-party-supplied CDEV before opening an endpoint. Failure to establish th connection first will cause opening an endpoint to fail. A new version of MacPPP should be available soon from the usual places to solve this problem for MacPPP users. Only the following MDEVS are supported: " InterSLIP", "InterPPP",
"InterPPP II", "TCP/IP PPP", "MacSLIP", and "MacPPP".
• The application "FTPd" currently does not work with TCP/IP MacTCP compatibility.
AppleTalk users :
• The settings "Load only when needed" have been disabled for this release of Open Transport for AppleTalk, but not for TCP/IP.
• Fixed-node support has been disabled for the first ship of Open Transport. It will reappear shortly for the general 1.1 release of Open Transport
